ArrowCDEF is a control definition (CDEF) that implements an up-down arrow like those seen in the color picker. It uses PICT resources as the arrow, so the arrows can be drawn as desired. There is both a black & white and a color set of PICT's in "ArrowCDEF Tester.π.rsrc" which you can use if you don't want to design you own.
Using ArrowCDEF
To use ArrowCDEF, just include the CDEF in your program's resource file and use it as you would any other control. When the control is created, the reference constant should contain the resource ID of an 'APIC' resource, which tells the control which PICT resources should be used to draw the arrow in each of it's four states–unhilighted, up arrow pressed, down arrow pressed and inactive. There is a TMPL resource in "ArrowCDEF Tester.π.rsrc" for editing 'APIC' resources.
ArrowCDEF only draws the arrow, it does not draw an indicator, or value of any kind. The application is responsible for updating and displaying any kind of value. See "ArrowCDEF Tester.c" for an example of how an action procedure is used to change and display the value of a control. ArrowCDEF uses the same part codes as the scroll bars. When the up arrow is pressed, "inUpButton" is the part code returned. "inDownButton" the part code returned when the down arrow is pressed.
The file "ArrowCDEF.h" defines some useful constants such as the CDEF resource ID, the control definition ID, the resource type that describes which PICTs to use for the arrow.
The file "ArrowCDEFUtils.c" contains some utilty routines for interfacing with the ArrowCDEF. Currently the only utilities available allow you to change the PICTs used to draw the arrow after it has been created. See the file "ArrowCDEFUtils.c" for details about how to use these functions.
Acknowledgements
Thanks to Eddy J. Gurney for his helpful advice. His Progress CDEF also served as the basis for the ArrowCDEF.
ArrowCDEF may be freely distributed, modified, included in any application or CD-ROM compilation, etc. as long as the following restrictions are met:
(1) This entire copyright notice remains intact when the source is redistributed, modified, etc.
(2) The copyright notice in the CDEF itself (the "copyright" string) remains intact.
David Hay hereby disclaims all warranties relating to this software, whether express or implied, including without limitation any implied warranties of merchantability or fitness for a particular purpose. David Hay will not be liable for any special, incidental, consequential, indirect or similar damages due to loss of data or any other reason, even if David Hay or an agent of his has been advised of the possibility of such damages. In no event shall David Hay be liable for any damages, regardless of the form of the claim. The person using the software bears all risk as to the quality and performance of the software.
US Governement:
Government End Users: If you are acquiring the Software and fonts on behalf of any unit or agency of the United States Government, the following provisions apply. The Government agrees:
(i) if the Software and fonts are supplied to the Department of Defense (DoD), the Software and fonts are classified as "Commercial Computer Software" and the Government is acquiring only "restricted rights" in the Software, its documentation and fonts as that term is defined in Clause 252.227-7013(c)(1) of the DFARS; and
(ii) if the Software and fonts are supplied to any unit or agency of the United States Government other than DoD, the Government's rights in the Software, its documentation and fonts will be as defined in Clause 52.227-19(c)(2) of the FAR or, in the case of NASA, in Clause 18-52.227-86(d) of the NASA Supplement to the FAR.
Revision History
1.1 – The following changes were made since release 1.0:
• Made some fairly minor changes to the CDEF itself.
• Added some utility routines to change the appearance of the CDEF dynamically.
• Ditched the GNU Public Licence in favor of one that is less restrictive and allow ArrowCDEF to be more widely used.
• Modified the test program to demonstrate the utility routines and added thorough comments.
1.0 – Initial release
Contacting the Author
If you have any comments, questions, improvements, or bug reports you can contact me in the following ways:
